Systems and methods for network inventory managment utilizing mobile technology

ABSTRACT

A system for streamlining a network management system (NMS) includes scanning, via a mobile device, a code on a hardware or software component; and determining, via the mobile device, whether the hardware or software component is a network component (NC), based on the scanned code. The hardware or software component may be a call manager, server, client device, interface card, repeater, hub, bridge, switch, router, or firewall, for example.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of application Ser. No. 13/481,184 filed on May25, 2012, the contents of all of which are hereby incorporated herein byreference in their entirety.

TECHNICAL FIELD

The present disclosure relates generally to network inventorymanagement.

BACKGROUND

A network management system (“NMS”) is a combination of hardware andsoftware used to monitor and administer a computer network. An NMSmanages network components (“NCs”) of a network (which can includehardware, firmware, and/or software components) and the channels used tocommunicate among the components and between the components and theoutside world. Typical aspects of an NMS include faults, configuration,accounting, performance, and security management. Tasks of an NMS mayinclude, for example, discovering network inventory, monitoring devicehealth and status, providing alerts to conditions that influence systemperformance, and identification of problems, their source(s), andpossible solutions.

Network inventory discovery involves identifying one or more NCs in anetwork. Once the NCs are discovered, the NMS can provide managementservices and applications related to the NCs to users and administratorsof the network. One existing approach to discovering network inventoryis through manually entering NCs. This process can be time consuming.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an example NMS;

FIG. 2 illustrates a block diagram of an example electronic device thatcan implement a network inventory management aspect of an example NMS;

FIG. 3 illustrates a block diagram of an example logic architecture thatcan implement a network inventory management aspect of an example NMS;and

FIG. 4 illustrates a flow chart of an example method for networkinventory management performed by the electronic device of FIG. 2.

FIG. 5 illustrates an example mobile device scanning an example NC codeand communicating the code to an example server of an example NMS.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

In one embodiment, a method for streamlining network inventorymanagement includes scanning, via a mobile device, a code on acomponent, such as a hardware or software component; and determining,via the mobile device, whether the hardware or software component is anetwork component (NC) of a particular network, based on the scannedcode. The component maybe a call manager, server, client device,interface card, repeater, hub, bridge, switch, router, or firewall, forexample.

The method may further include assigning the component to a network(therefore becoming a NC), via the mobile device, where the hardware orsoftware component is not a NC of the particular network. The assigningmay include identifying the component as a network component of theparticular network via the scanned code, and the scanned code maylogically link the component to the particular network. Because the NCmay be identified using a mobile device, a GPS component of the mobiledevice may trace location of the NC.

Also, the method may include requesting and assigning operationalparameters or characteristics of the NC, via the mobile device. Theoperational parameters or characteristics may include upload anddownload rates, bandwidth, power consumption, or buffer size, forexample.

Furthermore, the method may include communicating the operationalparameters or characteristics to a secured private network via a securedchannel. The secured private network may be a private cloudinfrastructure.

Example Embodiments

Various embodiments described herein can be used alone or in combinationwith one another. The following detailed description describes only afew of the many possible implementations of the present embodiments. Forthis reason, this detailed description is intended by way ofillustration, and not by way of limitation.

Advances in network management system (NMS) technologies have providedsolutions to allow network administrators to manage networks throughelectronic workstations and mobile devices. However, there is room foradvancements in the task of discovering and managing network components(NCs). Described herein is a network management system (NMS) forimproving discovery and management of NCs, utilizing advancements inmobile devices, bar code or serial number scanning, and networkinfrastructures. Particularly, in certain exemplary embodiments, the NMSmay utilize matrix bar code technologies and cloud computing tostreamline network inventory management.

For example, utilizing the NMS, a mobile device, such as a smart phone,can scan a matrix bar code on a hardware or software component and thendetermine whether the component is a NC or not. Where the component isnot a NC, the mobile device can assign the component to a network usingthe matrix bar code as an identifier. Once assigned through such aprocess or another process of assigning a hardware or software componentto a network, the component is considered an NC of the network to whichit is assigned and is identifiable via a mobile device via matrix barcode scanning as well. With respect to assigning a component to anetwork, such assigning can be made by associating a componentidentification code with a network identification code.

A hardware or software component may also be identifiable by a productidentification code, a serial number, IP address, or the like. Further,because a NC is identified using a mobile device in certain exemplaryembodiments, location of the NC can be tracked via a geographic locationmechanism, such as a global positioning system (GPS) component of themobile device. Because the mobile device can readily identify NCs usingits unique identifier, the mobile device is able to request operationalparameters or characteristics of a NC or submit operational parametersor characteristics of a NC to a storage device of the NMS, for example.Operational parameters or characteristics may include upload anddownload rates, bandwidth, power consumption, buffer size, for example.Also, the NMS can provide security and further streamline networkinventory management by storing the identifier and operationalparameters and characteristics of a NC in a storage device of a securedand private storage system, such as a cloud infrastructure storagesystem. A NC may include any single network node or group of networknodes. A NC may also be any hardware, software, or firmware networknode, including call managers, interface cards, repeaters and hubs,bridges, switches, routers, firewalls, for example.

FIG. 1 illustrates a block diagram of an example NMS 100. As shown, FIG.1, for example, includes a variety of networks, such as a first localarea network (LAN)/wide area network (WAN) 105 (e.g., a customerLAN/WAN) and wireless network 110, a variety of devices, such as clientdevice 107 and mobile devices 102 and 103, and a variety of servers,such as first server 106 (e.g., a customer server). Further the systemof networks 100 includes an intermediary network, such as the Internet115, that connects the first LAN/WAN 105 to a second LAN/WAN 120 (e.g.,a vendor LAN/WAN) that also includes a variety of devices (e.g., clientdevice 124) and servers (e.g., a second server 123 such as a vendorserver). In certain exemplary embodiments, customers and partners ofcustomers may only have access to the NMS 100 via devices of the firstLAN/WAN 105 and the wireless network 110; whereas, a vendor(s) of theNMS may only have access to the NMS via devices of the second LAN/WAN120. However, both the first LAN/WAN 105 and the second LAN/WAN 120 canshare information and commands of the NMS 100 via the connectionsdescribed herein. Although not depicted, the system of networks 100 mayalso include mass storage and other LANs or WANs or any other form ofarea networks such as a metropolitan area network (MAN), a storage areanetwork (SAN).

The system of networks 100 may couple network components so thatcommunications between such components can occur, whether communicationsare wire-line or wireless communications. Wire-line (such as a telephoneline or coaxial cable) and wireless connections (such as a satellitelink) can form channels that may include analog lines and digital lines.In communicating across such channels, the system of networks 100 mayutilize various architectures and protocols and may operate with alarger system of networks. Various architectures may include any varietyor combination of distributed computing architectures, including, a2-tier architecture (client-server architecture), an N-tierarchitecture, a peer-to-peer architecture, a tightly-coupledarchitecture, a service-oriented architecture (e.g., a cloud computinginfrastructure), a mobile-code-based architecture, areplicated-repository-based architecture, and so forth. Further, thevarious nodes of the system of networks 100 may provide configurationsfor differing architectures and protocols. For example, a router mayprovide a link between otherwise separate and independent LANs, and anetwork switch may connect two or more NCs or groups of NCs. Signalingformats or protocols employed may include, for example, TCP/IP, UDP, orthe like.

With respect to a wireless network, such as the wireless network 110,such a network may include stand-alone ad-hoc, mesh, Wireless LAN(WLAN), or a cellular network. A wireless network, such as network 110may further include a system of terminals, gateways, switches, routers,call managers, and firewalls coupled by wireless radio links. A wirelessnetwork may further employ a plurality of network access technologies,including Global System for Mobile Communication (GSM), Universal MobileTelecommunications System (UMTS), General Packet Radio Services (GPRS),Enhanced Data GSM Environment (EDGE), 3GPP Long Term Evolution (LTE),LTE Advanced, Wideband Code Division Multiple Access (WCDMA), Bluetooth,or 802.11b/g/n.

Networks (e.g., 105, 110, and 120) and devices (e.g., 102, 103, 106,107, 123, and 124) of the NMS 100 may be or include computational nodesof the NMS. For example, the aspects of the system of networks 100 canenable processing of different aspects of the NMS 100 on a plurality ofprocessors located at one or more of the computational nodes. Acomputational node may be one or more of any electronic device that canperform computations, such as a general-purpose computer, a mainframecomputer, a workstation, a desktop computer, a laptop computer, a mobiledevice, and so forth. Also, a computational node can include logic(e.g., client application logic 302, logic of the Internet 304, DMZlogic 306, and vendor service logic 310 depicted in FIG. 3). Logic mayinclude or interact with a knowledge base, such as a database.

Computational nodes of the NMS 100 may communicate network managementand inventory information and commands to a vendor services node(s)(e.g., the network 120), and vice versa. The vendor services node(s) mayinclude the vendor service logic 310 described below. Othercomputational nodes, such as customer nodes and partner nodes, mayinclude the client application logic 302 described below. One or more ofthe computational nodes of the NMS 100 may perform aspects of the method400. Instructions for performing these aspects of the method 400 mayexist in logic described herein.

FIG. 2 illustrates a block diagram of an example electronic device 200that can implement an aspect of an example NMS (e.g., the NMS 100).Instances of the electronic device 200 may be any client device orserver of the system of networks 100 or any device capable of becoming aNC. The electronic device 200, which can be a combination of multipleelectronic devices, may include a processor 202, memory 204, a powermodule 205, input/output 206 (including input/out signals, sensors, andinternal, peripheral, user, and network interfaces), a receiver 208 anda transmitter 209 (or a transceiver), an antenna 210 for wirelesscommunications, a global positioning system (GPS) component 214, and acommunication bus 212 that connects the aforementioned elements of theelectronic device 200. The processor 202 can be one or more of any typeof processing device, such as a central processing unit (CPU). Also, forexample, the processor 202 can be central processing logic; centralprocessing logic includes hardware, firmware, software and/orcombinations of each to perform a function(s) or an action(s), and/or tocause a function or action from another component. Also, based on adesired application or need, central processing logic may include asoftware controlled microprocessor, discrete logic such as anapplication specific integrated circuit (ASIC), aprogrammable/programmed logic device, memory device containinginstructions, or the like, or combinational logic embodied in hardware.Also, logic may also be fully embodied as software. The memory 204, suchas RAM or ROM, can be enabled by one or more of any type of memorydevice, such as a primary (directly accessible by the CPU) or asecondary (indirectly accessible by the CPU) storage device (e.g., flashmemory, magnetic disk, optical disk). The power module 205 contains oneor more power components, and facilitates supply and management of powerto the electronic device 200. The input/output 206, can include anyinterface for facilitating communication between any components of theelectronic device 200, components of external devices (such ascomponents of other devices of the system of networks 100), and users.For example, such interfaces can include a network card that is anintegration of the receiver 208, the transmitter 209, and one or moreI/O interfaces. The network card, for example, can facilitate wired orwireless communication with other nodes of the system of networks 100.In cases of wireless communication, the antenna 210 can facilitate suchcommunication. Also, the I/O interfaces, can include user interfacessuch as monitors, displays, keyboards, keypads, touchscreens,microphones, and speakers. Further, some of the I/O interfaces and thebus 212 can facilitate communication between components of theelectronic device, and in some embodiments ease processing performed bythe processor 202. In other examples of the electronic device 200, oneor more of the described components may be omitted.

Where the electronic device 200 is a client device, it can include acomputing device capable of sending or receiving signals, such as via awired or a wireless network. A client device may include, withoutlimitation, a desktop computer or a portable device, such as a smartphone, a tablet computer, a laptop computer, a wearable computer, or anintegrated device combining various features, such as features of theforgoing devices, or the like. Also, a client device may vary in termsof capabilities or features. For example, a smartphone or tabletcomputer device may include a physical or virtual keyboard, massstorage, an accelerometer, a gyroscope, a GPS, a digital camera, a touchsensitive color 2D or 3D display, or a combination thereof. Further, aclient device may include or may execute a variety of operating systems,including a personal computer operating system, such as a Windows orLinux, or a mobile operating system, such as iOS or Android. A clientdevice may also include or may execute a variety of possiblecommunications applications, such as email, short message service (SMS),or multimedia message service (MMS). A client device may also include orexecute a web browser that can perform a variety of possible tasks, suchas browsing, searching, playing various forms of media.

Where the electronic device 200 is a server, it can include a computingdevice that is capable of sending or receiving signals, such as via awired or wireless network, and may be capable of processing or storingsignals. Thus, devices capable of operating as a server may includededicated rack-mounted servers, desktop computers, laptop computers, settop boxes, integrated devices combining various features, such as one ormore features of the foregoing devices, or the like. Further, a servermay vary widely in configuration or capabilities, but generally, aserver may include one or more central processing units and memory thatmake possible the execution of a server type operating system, such asWindows Server, Mac OS X, or UNIX, for example.

FIG. 3 illustrates a block diagram of an example logic architecture 300that can implement an aspect of an example NMS (e.g., the NMS 100). Thelogic architecture may include client application logic 302, logic ofthe Internet 304, DMZ logic 306, and vendor service logic 310 thatincludes vendor service interface logic 311, single sign-in (SSO) logic312, and service application logic 313. In general, logic may besoftware, hardware, firmware, or a combination thereof.

The client application logic 302, which may be hosted by a client deviceof a customer, for example, may include application logic such as MobileNetwork Analytic, License Coverage, Mobile Service Request (SR)Management, Device Identification and Location Service, ContractMatching and Service Level Agreement (SLA), Mobile Communities,Partner/Cisco Certified Internetwork Experts (CCIE) IdentificationService, Smart Monitoring and Interaction, Mobile ReturnMerchandise/Material Authorization (RMA), Mobile Product Alert, andMobile Intellectual Capital (IC) Application, for example.

Mobile Network Analytic may provide analysis of collected data that mayproduce an action. An action may include capturing a faulty softwareimage/version and notifying network administrator to download a latestrelease of the software from a specific link, for example.

License Coverage may include software and hardware license compliancelogic and information, service agreement logic and information, andalerts and automatic updates of software for licensed customers/devices,for example. Using device credentials in the form of a uniqueidentifier, such as a validated serial number (SN) from a deviceidentification service, License Coverage may also provide the latestlicense agreement for a company from which service was initiated. Also,License Coverage may access partner databases and may include standardAPIs to integrate with various applications. As used herein the terms“serial number” and “SN” are used interchangeable with devicecredentials to describe a unique identifier of a device.

Mobile SR Management may include allowing authorized users to open newSRs, view and update SRs, and close SRs. Mobile SR Management may alsoinclude logic for monitoring and reporting on agreed performanceindicators related to the compliance. Mobile SR Management may includeservice desk logic that can be mobile. The service desk logic may beresponsible for acceptance, classification and handling of SRs regardinga mobile network and mobile technology. Further, Mobile SR Managementallows a customer or engineer to use a smart phone to enter, update, ormonitor the status of a SR. Mobile SR Management may require a user toregister first. The customer or administrator at a customer site mayenter a SR by scanning (or speaking or typing) a serial number/bar codeof a device or NC. Mobile SR Management may also allow a user to attach(e.g., by taking a picture and attaching) the pertinent device specificdata (e.g., data gathered by running “config” on a command lineinterface) of a device or NC. The pertinent data may then be encryptedand sent securely to a service provider's server, where an administratorcan then take action with respect to the SR.

Device Identification and Location Service may include client device andserver identification and authentication logic, device geographiclocation logic, such as GPS logic, and information regarding thelocation of a client device or server. Device Identification andLocation Service may allow/entitle users to scan (or enter by voice ortake a picture of the characters for optical character recognition wherescanning is not feasible) device credentials (e.g. SN, productidentification (PID)) using a portable communication device with imagecapture capabilities, such as a smart phone, and send pertinent datasecurely to a service provider's server. Device Identification andLocation Service may include collector logic for scanning the SNs andsending SNs to the service provider's server. Such information is usefulfor matching intellectual capital information.

Device Identification and Location Service may also correlate collectedinformation with WiFi access points or GPS located locations, forexample. This service may also send the correlation results securely toa customer's or service provider's server. Exact street address may beobtained by utilizing an access point or GPS located location.

Contract Matching and SLA may include access to any agreement relatedinformation, such as service level agreement information and logic. Theservice level agreement logic may include reporting features, forexample. Reporting features may include an ability to report contractrelated information per device or per network. Also reporting may be bya specific contract, contract type, contract status (e.g., activecontract), contract end date, and renewal options. Based on a scanned orentered SN (e.g., by voice or data entry on a smart phone), which may bevalidated using a SN service. User identification may be used to entitlea user via entitlement logic. Where a user is entitled, for example, theuser may have access to contract related information. In using theentitlement logic, users may be required to be entitled before sharingany contract related information. Also, entitlement may be validated viaan identification and password, for example. In some versions, avalidated SN may be shared without entitlement. Mobile Communities mayinclude mobile social networking logic that at least provides socialnetworking for individuals with similar interests to communicate withone another through their mobile device, such as a cell phone or tabletcomputer. Mobile social network logic may include and take advantage ofwireless network technologies including short message service (SMS),wireless application protocol, JAVA, Binary Runtime Environment forWireless (BREW), and other mobile internet services. Mobile socialnetwork logic may also include on wireless network technologies andfunctionalities that have been extended to multimedia and satellitenavigation including camera technologies and GPS integrated in mobiledevices. Also included may be Web 2.0 and Web 3.0 technologies relatedto mobile social networks that interact with cloud computing logic,user-generated content (UGC), location-based services (LBS), andaugmented reality (AR).

Partner/CCIE Identification Service may include expert information andservices for network support and administration, including informationon networks of particular providers, such as Cisco CertifiedInternetwork Experts and/or experts of partner technologies and networktechnologies in general. Such information may be per technology or perlocation, for example.

Smart Monitoring and Interaction may include personalize self-helplogic, and mobile related services for enhancing Mobile SR Management,for example. Functionally, such logic may allow customers or partners toview, track, or update SRs and device hardware or software updates.

Mobile RMA may include logic for authorizing and tracking returns,replacements, repairs, and receipts of network components via mobiletechnologies.

Mobile Product Alert may include summaries and notifications oftermination of service, termination of service support, bugs or viruses,other security alerts, and field notices from service provider supportstaff.

Mobile Intellectual Capital Application may include features that allowusers to enter or update intellectual capital rules.

Logic of the Internet 304 may include logic for a decentralized globalnetwork of networks, including logic for LANs, WANs, wireless networks,or public networks that allow signal packets to be communicated betweennetwork nodes of the foregoing networks. A signal packet communicatedvia the Internet may be routed via a path of gateways, servers, orrouters that may route the signal packet in accordance with a targetaddress and availability of a network path to the target address.

The DMZ logic 306 may include perimeter-networking logic that mayinclude and expose elements of the vendor service logic 310 to a largeruntrusted network and logic of the larger untrusted network, such as theInternet and its logic 304. The purpose of DMZ logic is to add anadditional layer of security to a network hosting the vendor servicelogic 310. For example, attackers external to the network hosting thevendor service logic 310 only have access to equipment and software ofthe DMZ logic, rather than any other part of the network.

The service application logic 313 may be hosted by a client device or aserver of an entity such as the vendor (also referred to as serviceprovider) providing the NMS. The service application logic 313 mayinclude service level contract information and logic, operations andbusiness logic (including manufacturing logic), and alerts for variousnetwork operational conditions, including alerts pertaining to securitybreaches, over use, and network and nodal operational failures, forexample. The service application logic 313 may also include a contractmanagement application for managing service level agreements (SLA).Input to the contract management application may include a device SN orPID, which may be scanned, typed, or spoken into a mobile device, forexample. Output of the contract management application may include avalidated SN and a contract identification number if the device subjectto a contract, for example. Also, where the device is subject to acontract, the output may include contract status, last day of support,contract type, and relevant contact information, for example.

FIG. 4 illustrates a flow chart of an example method 400 for inventorymanagement performed by the electronic device of FIG. 3, in accordancewith certain exemplary embodiments. The processor 302, for example, mayperform the method 400 by executing processing device readableinstructions encoded in the memory 304. The device readable instructionsencoded in the memory 304 may include some or all of the logic describedabove and depicted in FIG. 3.

The method 400 starts with a first network inventory management aspectof an NMS, such as a client device, identifying a customer network byassigning or discovering a unique inventory name or code for thecustomer network at 402. At 404, a second network inventory managementaspect of an NMS, such as a customer server and/or a vendor server of anNMS, may generate a mobile device scannable code, such as a matrix barcode, that includes the unique customer network name or code. Thescannable code may also include information pertaining to the customernetwork, such as an amount of NCs in the network and the date ofinitiating the network. The scannable code may also include inventorycollection information, which may include, for example, inventory for aparticular year, month, week, or date. The scannable code may beoutputted by an output device, such as printed out by a network printeror displayed by a display device, so that it can be posted in a datacenter of the network or on an NC of the network.

At 406, the second network inventory management aspect may assign aunique inventory name or code for a NC, and at 408, the second networkinventory management aspect may assign the NC to the customer network.At 410, the second network inventory management aspect may generate ascannable code, such as a matrix bar code, that may contain the uniquecustomer network name or code, the unique name or code for the NC,network information, information specific to the NC, or a combinationthereof. The scannable code for the NC then may be outputted by anoutput device, such as printed out by a printer, so that it can beposted on an NC of the network. The NC's scannable code may also beoutputted from a display device, an audio output device, or the like,upon request.

For NCs that already have a unique scannable code, the first networkinventory management aspect may assign the NC to the customer network byat least scanning the unique scannable code of the NC. The first networkinventory management aspect may also assign the NC to the customernetwork by at least scanning the unique scannable code of the NC andthen receiving input including the network name or code of the network.For example, the NC can be assigned by scanning the unique scannablecode of the NC via an optical sensor of a mobile device, and thenscanning the unique scannable code of the network via the optical sensorof the device, receiving the network code via a keypad of the device, orreceiving the network code via a microphone of the device. Also, insteadof receiving the NC's identification code via a scan by the opticalsensor of the mobile device, the code may be received via the keypad ormicrophone of the mobile device. The scanning and other forms ofentering codes may occur via an optical sensor, keypad, microphone,and/or the like of the input/output 206 illustrated in FIG. 2. Anadvantage of using a mobile device for scanning or entering the uniquescannable code is that location of the NC can be automaticallydetermined via a GPS component of the mobile device. With respect to thelocations of the codes, the unique scannable code of the network may beon a network switch chassis, and the unique scannable code of the NC maybe on a card of the chassis, for example.

Instead of or in addition to processes 406 through 410, NCs may bediscovered via any other form of NC discovery. Discovery of an NC andcollection of information pertaining to the NC may include performingsuch tasks via a command line interface, for example. In such as case,running a command line interface command, such as “config”, may lead todiscovery of an NC. Typically when running “config”, output may includea list of cards for a given chassis, router, or switch, for example.Also, discovery of an NC may come through searching managementinformation bases (MIBs) via SNMP, for example. Further, a collector(typically software) may collect data on a customer network or oncomponents of that network on a periodic basis. Once collected the datamay be transmitted securely to storage logic of service providernetwork. A collector may be configured to discover NCs that it collectsinformation on or it may be given identifiers of the NCs (e.g., IPaddresses), so discovery may not be necessary.

At 412, a transmitter of the first network inventory management aspect,for example, may transmit the unique inventory names or codes for thenetwork and NCs to a NMS service provider vendor network, such as vendorLAN/WAN 120. Also, the transmitter, for example, may transmit networkand specific NC information to the vendor LAN/WAN 120. Thecommunications of this information may be transmitted over a securetransport mechanism, such as using the DMZ logic 306, which may includeencryption. At 414, the unique inventory names or codes for the networkand NCs and related data may be validated and correlated, via the secondnetwork inventory management aspect, to contract and intellectualcapital information, stored in the service application logic 313, forexample. Further, the validation and correlation may be performed by anaspect of the service application logic 313. Prior to validation andcorrelation, in cases where a collector or mobile device outside of anetwork collects the NCs and related data, such a collector or mobiledevice may be need to be authenticated by a security technology toensure the collector or mobile device is authorized by the network.Also, a user prior to using the collector or mobile device for suchfunctionality may also need to be authenticated by the securitytechnology.

Finally, at 416, the second network inventory management aspect mayupdate the unique inventory names or codes for the network and NCs andrelated data that was transmitted to the vendor LAN/WAN 120. Relateddata may include data generated from one of the various components ofthe client application logic 302 or the service application logic 313.At 418, such data updated in the vendor service logic 310 may bereported back to the customer LAN/WAN 105 via the second networkinventory management aspect, and then in turn be received by a mobiledevice connected to the customer LAN/WAN. This information reported tothe customer LAN/WAN 105 may include alerts and notifications regardingoperating conditions and various status information of the customernetwork or an NC of the network. The information may include contractcoverage, administrative support information, security issues, and bugs,for example. The information may also include data related to MobileNetwork Analytic, License Coverage, Mobile SR Management, DeviceIdentification and Location Service, Contract Matching and SLA, MobileCommunities, Partner/CCIE Identification Service, Smart Monitoring andInteraction, Mobile RMA, Mobile Product Alert, and Mobile ICApplication, for example.

By integrating a mobile device with a NMS (e.g., the NMS 100), thebenefit of this last process at 418 may be available from anywhere thatthe mobile device can receive telecommunications service. Besides, beingable to interact with an NMS from any location having telecommunicationsservice, by integrating mobile technology, the NMS becomes locationaware via a GPS component of the mobile technology. Further, theportability of mobile device allows on-site diagnosis of NCs andprogress tracking of shipped NCs, with respect to location and repairstatus, for example. As suggested the benefits of integrating mobiledevice technology with an NMS is endless.

FIG. 5 illustrates an example mobile device 502 scanning an example NCcode 508 and communicating the code 508 to an example server 510 of anexample NMS 512, in accordance with certain exemplary embodiments. Forexample, the mobile device 502 can scan the code 508 via an opticalsensor 504 (e.g., a digital camera) and communicate the code 508 via atransceiver 506 of the device 200, in certain exemplary embodiments. Asillustrated in FIG. 5, the example bar code may include a matrix barcode. A person of ordinary skill in the art will recognize that the code508 can include different or other elements (which may or may notinclude matrix bar codes) in alternative exemplary embodiments. Theserver 510 may communicate information pertaining to a respective NCassociated with the NC code 508 to the mobile device 502, which may bereceived by the transceiver 506. In certain alternative exemplaryembodiments, the mobile device 502 may also be an aspect of the NMS 512.

Various embodiments described herein can be used alone or in combinationwith one another. The foregoing detailed description has described onlya few of the many possible implementations of the present embodiments.For this reason, this detailed description is intended by way ofillustration, and not by way of limitation.

1-20. (canceled)
 21. A method, comprising: receiving, at a mobile device, an input of a code associated with an electronic component; and determining, by the mobile device, whether the electronic component is a component of a network, based on comparing the code against inventory data associated with the network.
 22. The method of claim 21, wherein the input of the code includes audio information representative of the code.
 23. The method of claim 21, wherein the input of the code includes graphical information representative of the code.
 24. The method of claim 21, wherein the receiving of the input of the code includes receiving a voice command including the code.
 25. The method of claim 21, wherein the receiving of the input of the code includes receiving a photographed image including the code.
 26. The method of claim 21, wherein the receiving of the input of the code includes receiving a scanned image including the code.
 27. The method of claim 21, further comprising: assigning, by the mobile device, the electronic component to the network in response to determining, by the mobile device, that the electronic component is not a network component of the network.
 28. The method of claim 27, wherein the assigning comprises identifying the electronic component as a component of the network by the code and logically linking the electronic component to the network.
 29. The method of claim 21, further comprising: requesting at least one of operational parameters or characteristics of the electronic component, by the mobile device.
 30. The method of claim 21, further comprising: assigning at least one of operational parameters or characteristics of the electronic component, by the mobile device.
 31. A system comprising: a processing device configured to: read an inputted code associated with an electronic component, the electronic component being one or more of a software component or hardware component, the inputted code derived from a voice command; and determine whether the electronic component is a network component of a network, based on the inputted code.
 32. The system of claim 31, wherein the processing device is further configured to: validate the inputted code against service level agreement information.
 33. The system of claim 31, wherein the processing device is further configured to: validate the inputted code against intellectual capital information.
 34. The system of claim 31, wherein the processing device is further configured to: validate the inputted code against social media information.
 35. The system of claim 31, wherein the processing device is further configured to: assign the electronic component to the network, in response to determining that the electronic component is not a network component of the network; and receive a notification regarding operating conditions of the electronic component with respect to the network.
 36. A non-transitory memory device having stored thereon processor executable instructions that, in response to execution by a processor, cause the processor to perform operations comprising: identifying an electronic component; assigning a network code associated with a network to the electronic component; assigning a unique inventory code to the electronic component; and generating a graphic corresponding to the network code and the unique inventory code.
 37. The non-transitory memory device of claim 36, wherein the executable instructions, in response to execution by a processor, cause the processor to perform operations comprising: associating the network code and the unique inventory code with contract and intellectual capital information.
 38. The non-transitory memory device of claim 36, wherein the executable instructions, in response to execution by a processor, cause the processor to perform operations further comprising: associating the graphic with inventory data associated with the network.
 39. The non-transitory memory device of claim 36, wherein the graphic includes text corresponding to the network code and the unique inventory code.
 40. The non-transitory memory device of claim 36, wherein the graphic includes a barcode corresponding to the network code and the unique inventory code. 